DOC-17057: Remove inline cockroach issue/PR links from docs prose#23306
DOC-17057: Remove inline cockroach issue/PR links from docs prose#23306ebembi-crdb wants to merge 3 commits into
Conversation
Unlink 292 docs pages by removing markdown hyperlinks to cockroach issues and PRs, keeping the #NNNNN reference text. This is the catch-all for link-only changes not covered by the more specific release notes, known limitations, advisories, or other targeted PRs. Part of DOC-17057. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
✅ Deploy Preview for cockroachdb-interactivetutorials-docs canceled.
|
|
✅ Cross-Version Link Check Passed All cross-version link issues have been resolved. Good job! |
✅ Deploy Preview for cockroachdb-api-docs canceled.
|
Files changed:
|
✅ Netlify Preview
To edit notification comments on pull requests, go to your Netlify project configuration. |
- Replace hardcoded ../v23.1/*.html relative links with
{% link {{ page.version.version }}/... %} tags in
_includes/v{23.2-25.3}/backward-incompatible/alpha.1.md
(matching the pattern already used in v24.3)
- Replace hardcoded images/v24.2/geospatial/st_union.png with
images/{{ page.version.version }}/geospatial/st_union.png
in st_union.md for v25.1 and v25.3
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Use absolute /docs/images/ path with {{ page.version.version }} instead
of nesting {{ }} inside {{ }} (which Liquid can't evaluate).
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
rmloveland
left a comment
There was a problem hiding this comment.
needs a fair amount of work, please see my comments
in general, removing link targets is not sufficient. in most cases, we need to remove the entire sentences of the form "Tracking github issue", "for more information, see #xxx", etc.
| @@ -1 +1 @@ | |||
| [`ROLLBACK TO SAVEPOINT`](rollback-transaction.html#rollback-a-nested-transaction) (for either regular savepoints or "restart savepoints" defined with `cockroach_restart`) causes a "feature not supported" error after a DDL statement in a [`HIGH PRIORITY` transaction](transactions.html#transaction-priorities), in order to avoid a transaction deadlock. For more information, see GitHub issue [#46414](https://www.github.com/cockroachdb/cockroach/issues/46414). | |||
| [`ROLLBACK TO SAVEPOINT`](rollback-transaction.html#rollback-a-nested-transaction) (for either regular savepoints or "restart savepoints" defined with `cockroach_restart`) causes a "feature not supported" error after a DDL statement in a [`HIGH PRIORITY` transaction](transactions.html#transaction-priorities), in order to avoid a transaction deadlock. For more information, see GitHub issue #46414. | |||
There was a problem hiding this comment.
removing the link target is not sufficient - please remove the entire "for more information, see github issue #xxx "
| @@ -1 +1 @@ | |||
| A changefeed in [Avro format]({% link {{ page.version.version }}/changefeed-messages.md %}#avro) will not be able to serialize [user-defined composite (tuple) types](create-type.html). [Tracking GitHub Issue](https://github.com/cockroachdb/cockroach/issues/102903) No newline at end of file | |||
| A changefeed in [Avro format]({% link {{ page.version.version }}/changefeed-messages.md %}#avro) will not be able to serialize [user-defined composite (tuple) types](create-type.html). Tracking GitHub Issue No newline at end of file | |||
There was a problem hiding this comment.
removing the link target is not sufficient. please remove this and all other instances of "Tracking Github issue"
| CockroachDB is a [distributed SQL](https://www.cockroachlabs.com/blog/what-is-distributed-sql/) database built on a transactional and strongly-consistent key-value store. It **scales** horizontally; **survives** disk, machine, rack, and even datacenter failures with minimal latency disruption and no manual intervention; supports **strongly-consistent** ACID transactions; and provides a familiar **SQL** API for structuring, manipulating, and querying data. | ||
|
|
||
| CockroachDB is inspired by Google's [Spanner](http://research.google.com/archive/spanner.html) and [F1](http://research.google.com/pubs/pub38125.html) technologies, and the [source code](https://github.com/cockroachdb/cockroach) is freely available. | ||
| CockroachDB is inspired by Google's [Spanner](http://research.google.com/archive/spanner.html) and [F1](http://research.google.com/pubs/pub38125.html) technologies, and the source code is freely available. |
There was a problem hiding this comment.
please remove ", and the source code is freely available" - here and in all other versions where it appears in this file
|
|
||
| {{site.data.alerts.callout_info}} | ||
| The amount of remaining disk space on other nodes in the cluster is not yet considered as part of the decommissioning pre-flight checks. For more information, see [cockroachdb/cockroach#71757](https://github.com/cockroachdb/cockroach/issues/71757) | ||
| The amount of remaining disk space on other nodes in the cluster is not yet considered as part of the decommissioning pre-flight checks. For more information, see cockroachdb/cockroach#71757 |
There was a problem hiding this comment.
please remove the "For more information, see" sentence entirely
| @@ -1 +1 @@ | |||
| [`ROLLBACK TO SAVEPOINT`]({% link {{ page.version.version }}/rollback-transaction.md %}#rollback-a-nested-transaction) (for either regular savepoints or "restart savepoints" defined with `cockroach_restart`) causes a "feature not supported" error after a DDL statement in a [`HIGH PRIORITY` transaction]({% link {{ page.version.version }}/transactions.md %}#transaction-priorities), in order to avoid a transaction deadlock. For more information, see GitHub issue [#46414](https://www.github.com/cockroachdb/cockroach/issues/46414). | |||
| [`ROLLBACK TO SAVEPOINT`]({% link {{ page.version.version }}/rollback-transaction.md %}#rollback-a-nested-transaction) (for either regular savepoints or "restart savepoints" defined with `cockroach_restart`) causes a "feature not supported" error after a DDL statement in a [`HIGH PRIORITY` transaction]({% link {{ page.version.version }}/transactions.md %}#transaction-priorities), in order to avoid a transaction deadlock. For more information, see GitHub issue #46414. | |||
There was a problem hiding this comment.
removing the link target is not sufficient. please remove "for more information, see github issue #xxx " - here and elsewhere
| If you have corrupted data in a database or table, [restore]({% link {{ page.version.version }}/restore.md %}) the object from a prior [backup]({% link {{ page.version.version }}/backup.md %}). If revision history is in the backup, you can restore from a [point in time]({% link {{ page.version.version }}/take-backups-with-revision-history-and-restore-from-a-point-in-time.md %}). | ||
|
|
||
| Instead of dropping the corrupted table or database, we recommend [renaming the table]({% link {{ page.version.version }}/alter-table.md %}#rename-to) or [renaming the database]({% link {{ page.version.version }}/alter-database.md %}#rename-to) so you have historical data to compare to later. If you drop a database, the database cannot be referenced with `AS OF SYSTEM TIME` queries (see [#51380](https://github.com/cockroachdb/cockroach/issues/51380) for more information), and you will need to take a backup that is backdated to the system time when the database still existed. | ||
| Instead of dropping the corrupted table or database, we recommend [renaming the table]({% link {{ page.version.version }}/alter-table.md %}#rename-to) or [renaming the database]({% link {{ page.version.version }}/alter-database.md %}#rename-to) so you have historical data to compare to later. If you drop a database, the database cannot be referenced with `AS OF SYSTEM TIME` queries (see #51380 for more information), and you will need to take a backup that is backdated to the system time when the database still existed. |
There was a problem hiding this comment.
please remove the parenthetical "(see #XXX for more info)" here and in all other versions
|
|
||
| 1. You haven't created any indexes at all yet. The query is likely to be doing full table scans, which you will need to hunt down with [`EXPLAIN`]({% link {{ page.version.version }}/explain.md %}). | ||
| 1. CockroachDB does not yet have built-in support for index-based nearest neighbor queries. If this feature is important to you, please comment with some information about your use case on [cockroachdb/cockroach#55227](https://github.com/cockroachdb/cockroach/issues/55227). | ||
| 1. CockroachDB does not yet have built-in support for index-based nearest neighbor queries. If this feature is important to you, please comment with some information about your use case on cockroachdb/cockroach#55227. |
There was a problem hiding this comment.
please remove the sentence "if this feature is important to you, ..." on this and all other versions of this page
|
|
||
| {{site.data.alerts.callout_info}} | ||
| {% include feature-phases/preview.md %} For details, see the tracking issue [cockroachdb/cockroach#46260](https://github.com/cockroachdb/cockroach/issues/46260). | ||
| {% include feature-phases/preview.md %} For details, see the tracking issue cockroachdb/cockroach#46260. |
There was a problem hiding this comment.
please remove "for details ..." here and elsewhere
| ### Check for constraint violations with `SCRUB` | ||
|
|
||
| Checks the consistency of [`UNIQUE`]({% link {{ page.version.version }}/unique.md %}) indexes, [`CHECK`]({% link {{ page.version.version }}/check.md %}) constraints, and more. Partially implemented; see [cockroachdb/cockroach#10425](https://github.com/cockroachdb/cockroach/issues/10425) for details. | ||
| Checks the consistency of [`UNIQUE`]({% link {{ page.version.version }}/unique.md %}) indexes, [`CHECK`]({% link {{ page.version.version }}/check.md %}) constraints, and more. Partially implemented; see cockroachdb/cockroach#10425 for details. |
There was a problem hiding this comment.
please remove everything after the semicolon after "Partially implemented; ..." here and in all other versions of this page
| The following diagram presents the same set of schema objects as the previous outline-style diagram, but using boxes and lines joined with arrows that represent the "top-down" view. | ||
|
|
||
| Each box represents a schema object in the zone configuration inheritance hierarchy. Each solid line ends in an arrow that points from a parent object to its child object, which will inherit the parent's values unless those values are changed at the child level. The dotted lines between partitions and sub-partitions represent the known limitation mentioned previously that sub-partitions do not inherit their values from their parent partitions. Instead, sub-partitions inherit their values from the parent table. For more information about this limitation, see [cockroachdb/cockroach#75862](https://github.com/cockroachdb/cockroach/issues/75862). | ||
| Each box represents a schema object in the zone configuration inheritance hierarchy. Each solid line ends in an arrow that points from a parent object to its child object, which will inherit the parent's values unless those values are changed at the child level. The dotted lines between partitions and sub-partitions represent the known limitation mentioned previously that sub-partitions do not inherit their values from their parent partitions. Instead, sub-partitions inherit their values from the parent table. For more information about this limitation, see cockroachdb/cockroach#75862. |
There was a problem hiding this comment.
please remove "for more about this limitation, see ..." here and on all other versions of this page
Summary
#NNNNNreference text; only the hyperlinks are removedThis is PR 3 of 10 splitting #23256 into reviewable chunks.
Jira: DOC-17057
Test plan
🤖 Generated with Claude Code